feat: add experimental tsdown #1
Open
+2,883
−1,471
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ok, looks like Nuxt changing some internals at build time (or maybe the PROD env.), tsdown unable to generate/emit dts files, I need to check what's required here: 
|
chore: use tsconfig.json from nuxt build at tsdown build
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Crazy experiment to generate statically analisable configuration. Works fine with the
prepare command.Pending tasks:
split tsdown build per templaterequires previous step or find a way to do that (ask Daniel): not sure if we can generate virtual Nuxt module using just the ts file, maybe something we need to add at Nuxt (or maybe already there: we need to genarate the corresponding dts)pnpm dev:preparetoo slow ~2 seconds => HMR is quite fast ~210ms (check screenshot below)magicastto allow use local variables and load module meta info before merging (rn merging on the fly); we need to load meta data and then add the configurationNOTE: I'll need to change the logic, we're sharing
ssr,optionsandunocssvirtual modules, there is a race condition on HMR and on SSR build:nuxt prepareruns globally, but HMR and SSR build will run 2 "builds", maybe @danielroe can help on thisRunning
pnpm devwill run the prepare command a few times.The external playground not updated, this PR using a local tgz of Vuetify: vuetifyjs/vuetify#22152
HMR